| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.4.2.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.4.2 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_4_2_Support_for_Communications_Within_an_Organization |
| Title | AS.4.2 Support for Communications Within an Organization (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Facilitate communications regarding patient data and status within a health care organization. |
| Purpose | There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders between clinical systems in the facility (e.g., ambulatory, inpatient and ED). |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Facilitate communications regarding patient data and status within a health care organization.
There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders between clinical systems in the facility (e.g., ambulatory, inpatient and ED).
| AS.4.2#01 | SHOULD |
The system SHOULD provide the ability to render patient status tracking data on patient status devices or other patient tracking systems. |
| AS.4.2#02 | SHOULD |
The system SHOULD determine and render patient information appropriate to the care setting, and/or the patient's condition, on status/patient/tracking displays. |
| AS.4.2#03 | SHOULD |
The system SHOULD render patient information that can be used for status and patient tracking systems (e.g., tracking display, ED status board) that displays, as a minimum: patient identification, patient location, medical condition, care process status, study status, vital signs, and inter-staff communication notes as applicable. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.4.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Facilitate communications regarding patient data and status within a health care organization.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders between clinical systems in the facility (e.g., ambulatory, inpatient and ED).</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.4.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render patient status tracking data on patient status devices or other patient tracking systems.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.4.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD determine and render patient information appropriate to the care setting, and/or the patient's condition, on status/patient/tracking displays.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.4.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD render patient information that can be used for status and patient tracking systems (e.g., tracking display, ED status board) that displays, as a minimum: patient identification, patient location, medical condition, care process status, study status, vital signs, and inter-staff communication notes as applicable.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.4.2",
"version" : "2.1.0",
"name" : "AS_4_2_Support_for_Communications_Within_an_Organization",
"title" : "AS.4.2 Support for Communications Within an Organization (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Facilitate communications regarding patient data and status within a health care organization.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "There needs to be an ability to communicate patient data and status (e.g., patient history, patient physical examination), discrete clinical data (e.g., blood pressure, pulse, temperature, pulse oximetry, laboratory data, microbiology data, radiology data), and orders between clinical systems in the facility (e.g., ambulatory, inpatient and ED).",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.4.2-01",
"label" : "AS.4.2#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render patient status tracking data on patient status devices or other patient tracking systems."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.4.2-02",
"label" : "AS.4.2#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD determine and render patient information appropriate to the care setting, and/or the patient's condition, on status/patient/tracking displays."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.4.2-03",
"label" : "AS.4.2#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD render patient information that can be used for status and patient tracking systems (e.g., tracking display, ED status board) that displays, as a minimum: patient identification, patient location, medical condition, care process status, study status, vital signs, and inter-staff communication notes as applicable."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.